I see actions/setup-python@v5 is being used here. In my own CI I've just switched to letting uv handle the Python installation for me.

Thanks! I'd be open to switching to setup-uv here.

Yeah, I think when we first started using uv in parts of this workflow, uv wasn't yet able to install Python for you and setup-uv didn't yet exist (just the curl command). I'm also open to modernising it a bit!

I switched everything to astral-sh/setup-uv, let me know how it looks!

For the ones where we're manually uv pip installing dependencies, I think you'll need to create a virtual environment to pip install them into (the --system flag for uv pip install won't work if we're using a uv-managed Python installation).

You'll also need to pin the action to an exact hash to make zizmor happy in pre-commit, I think!